Skip to main content
TrustRadius
Paligo

Paligo

Overview

What is Paligo?

Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.

Read more
Recent Reviews

Paligo delivers

8 out of 10
December 20, 2022
We use Paligo to generate all external-facing, technical documentation, including hardware manuals, software reference material, and …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Paligo?

Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.

Entry-level set up fee?

  • Setup fee optional
For the latest information on pricing, visithttps://paligo.net/pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

47 people also want pricing

Alternatives Pricing

What is MadCap Flare?

MadCap Software, headquartered in La Jolla, offers MadCap Flare, a help authoring and technical writing tool featuring onboarding and support from MadCap, and a set of modules for designing advanced guides, aids, and web or application help aids.

What is Ibexa DXP?

Ibexa, headquartered in Oslo, helps B2B companies to stay relevant and succeed by transforming traditional sales strategies into frictionless buying experiences, with their eponymous digial experience platform (DXP).

Return to navigation

Product Details

What is Paligo?

Paligo is an enterprise-grade cloud-based Component Content Management System (CCMS) with single-sourcing content reuse for technical documentation, training content, policies and procedures, and knowledge management. Paligo is 100% XML in the back end, based on a modified version of DocBook - an established open standard developed for technical documentation. This is to provide future-proofing as well as extensibility and transformability for any current and future applications. The strict structure of XML and solid validation it provides offers possibilities and a consistency that, according to Paligo, no other format can provide.

Companies seek to make their documentation more efficient through single-sourcing and reuse. But many single-sourcing projects fail due to the steep learning curves and costs of implementation of traditional systems. So cloud-based solutions like Paligo aim to enable greater collaboration and efficiency. Using modern web technology reduces the costs of implementation, to increase usability and thereby user acceptance. A cloud-based authoring and publishing platform to reuse and single-source documentation with a clear focus on usability and user acceptance can improve the chance of realizing the return of investment and actually achieving the increase in efficiency.

In an information-enabled world, content is required to help solve problems and guide decision-making. Siloed content creation and management technology have led to content duplication, inconsistent content, and challenges finding the right content for customer and employee experiences. A component content management system (CCMS) like Paligo aims to change that.

Paligo's top features at a glance:

  • Structured Authoring

Structured authoring helps make content consistent, accurate, and future-proof. The XML editor enables content reuse, making structured authoring easier.

  • Content Reuse

Reuse content at scale with topic-based authoring and smart single sourcing features such as component reuse, block content reuse, the Paligo text fragment reuse, dynamic variables, and conditional content.

  • Multi-Channel Publishing

Paligo takes multi-channel publishing to another level. Publish to HTML5, PDF print, SCORM eLearning, Zendesk, Salesforce, GitHub, BitBucket, Amazon S3, and much more.

  • Versioning

Paligo features version history and roll-back, version branching, and release management made specifically for technical writers and content authors.

  • Translation Management
Paligo offers smart translation management, avoiding duplicate files for each language. Integrates with Memsource and other TMS solutions.

Paligo Features

  • Supported: Single sourcing
  • Supported: Content reuse
  • Supported: Multi-channel publishing
  • Supported: Translation management
  • Supported: Contributor editor
  • Supported: Structured authoring
  • Supported: Topic based authoring
  • Supported: Versioning
  • Supported: Branching
  • Supported: Assignment planner
  • Supported: REST API
  • Supported: Variables
  • Supported: Conditional content
  • Supported: CCMS
  • Supported: Integrations
  • Supported: XML editor
  • Supported: Docbook

Paligo Screenshots

Screenshot of Branching in PaligoScreenshot of Conditional filters in PaligoScreenshot of Contributor editor in PaligoScreenshot of Some of the integration options in PaligoScreenshot of Main editor in PaligoScreenshot of Multi-channel publishing options in PaligoScreenshot of Assignment planner in PaligoScreenshot of Content reuse in PaligoScreenshot of SME reviewing in PaligoScreenshot of Translations in PaligoScreenshot of Versioning in Paligo

Paligo Videos

A quick, high-level look inside Paligo.
An in-depth look at the best-in-class Paligo <> Zendesk integration.

Paligo Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported CountriesGlobal
Supported LanguagesEnglish

Frequently Asked Questions

Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.

Heretto, Vasont CCMS, and MadCap IXIA CCMS are common alternatives for Paligo.

Reviewers rate Support Rating highest, with a score of 8.5.

The most common users of Paligo are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(34)

Attribute Ratings

Reviews

(1-10 of 10)
Companies can't remove reviews or game the system. Here's why
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Making a gigantic manual for our software.
  • Filtering & Versioning.
  • Inbuilt Teaching of Component-based structuring.
  • Layout Editing.
  • Simple to start using, high skill ceiling/complexity if necessary.
  • Small ease of use improvements, e.g., colored root folders.
  • Multi-Topic review assignments/Topic section reviews.
It is the best tech writing software I've used for learning and mastering component-based tech writing/documentation.
August 31, 2023

Another happy customer

Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Paligo for our technical documentation (not the rest of our website). This includes:
  • HTML output for our public website (help center)
  • PDF output for selected customers or internal use.
  • In the future, we plan to allow users to log in to the doc portal so they see only the documentation that is relevant to them.
  • Content re-use
  • Full flexibility in HTML (and other) output
  • In my opinion, the user dashboard has minor issues
  • In my opinion, reviewing is clumsy - reviewers need changes highlighted and view everything in preview mode only
  • Better documentation - In my opinion, we have to rely too much on our customer service rep
It suits our needs very well - I have not considered other possible uses.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We needed to scale our efforts in documentation through content creation and process management, improve our offering to our user base, and manage translations. Paligo helped us address all these issues, and more. In terms of scope, our entire user base of approximately 5000 people will get direct access to the content we manage in Paligo. Internally we started to use Paligo through our Customer Success department, and now our product and development departments have become very familiar with this first class CCMS. Consequently, we are able to integrate content we create in Paligo into our own product, via very easy to use element attributes in Paligo. So now our user base can access our content via the internet, and our product. I have to say, our work was made very easy with the excellent, direct and proactive CS team (and more) of Paligo. This has been a very happy experience.
  • Content creation
  • Content management
  • Content reuse
  • Content versioning (this is a dream)
  • Content translation
  • Content presentation
  • Customer support
  • Paligo offers a comprehensive theme and style management editor, but you need to be a proficient user of CSS and associated to work this well.
  • Access rights to content for normal users could be broadened.
I think Paligo should be considered a strong competitor to Zendesk's Guide. I believe this platform is a good fit for Marketing campaigns, Knowledge Management, Sales and the integration of many 3rd parties. It is not a content/product/team management tool, and so would not be a good replacement for something like Confluence and its related 3rd parties.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
I use Paligo to create publicly accessible Guides, Tutorials, and visual Walkthroughs supporting our industrial automation software. These need to be suitable for product marketing, building excitement/confidence during pre-sales, and supporting new and long-time users of our product(s). Across these different use cases, articles are consumed by Management, Supervisors / Operators, Trainers, and Engineers. Users interact with our product across multiple platforms: inside our software, in our Paligo-based help pages, and in our Learning Management System. In order to avoid duplicating or creating contradictory product information, we need to be able to author in a single location, with content and style outputs conditioned by the platform.
  • Conditional formatting.
  • Tracking text reuse.
  • Informal topics / components.
  • User interactions.
  • SCORM 1.2 compatibility.
  • Unlinking / editing reused text is unintuitive.
  • WHEN I COPY A TOPIC, REUSE THE PARAS INSIDE IT!
Paligo fits my use case very well (product training materials with a consistent, highly-visual style). There are some arbitrary limitations on how components can be structured - which can be tedious - but most of what I want to do is very straightforward.
Ricardo Jorge Da Costa Lima | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Paligo is used on a daily basis by our technical writer. It serves as the central tool to create new and update existing manuals. These manuals are intended to guide users through our software.
  • The review mode is super convenient. Comparing a snapshot of the previous versions with the current one clearly outlines the respective changes and reduces the necessary content to review tremendously.
  • The option to reuse text fragments is another handy feature. Text fragments will be updated whenever the original text fragment is altered is also extremely helpful.
  • Managing a content's structure was never easier. An intuitive drag & drop functionality allows you to design your document's structure however you like.
  • You can also fork content, in addition to reuse text fragments. This is another helpful option that no longer requires you to create repetetive chapters over and over.
  • The option to comment within the previously praised review mode is quite tricky as it only provides a minimal dialog box. Additionally, extended filter functionalities for comments in general and basic formatting feat. would also be helpful in case the author and reviewer are not physically located in the same office and have to rely on these comments.
  • Paligo provides a preview mode that is convenient to a certain degree. However, the formatting of images is quite critical as their formatting (such as width) is not accurately reflected in the preview mode and therefore requires a subsequent review when the document is exported.
  • The also previously praised "Reuse text fragments" function can also be improved. It may be a helpful and handy feature, but; the search criteria that must be entered to find text fragments must be improved because it does not consider hyphens. Additionally, the order of returned results is not consistent therefore quite tedious to use.
  • For every day or stand-alone words, this is therefore almost impossible and causes unnecessary extra work, causing one to check multiple recommended sources only to realize none of them is the desired one and subsequently disregarding the reusing of text.
  • This eventually becomes even more tedious when revising documents where text was not reused due to the above-described scenario.
  • In addition, allowing users to merge one text fragment with another text fragment that matches 100% would result in a reduced effort for the user to edit reused text fragments. It can also be helpful for cleaning up lack-of-reuse artifacts created by inexperienced Paligo users.
  • A general flowchart functionality to visualize the overall procedure of our software would be a huge improvement.
Well-Suited:
  • Updating existing content based on comments made in review mode
  • Determine locations in which text fragments are reused
  • Layout Design conveniently to set up a template for your documents. A variety of settings and features allow you to customize your layout to your desire.
Less Appropriate:
  • Visualizing processes with Flowcharts
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Paligo to manage technical documentation for approximately 20 different software products. We serve multiple markets and have both cloud and on-premise versions right now, so we have a need to reuse a lot of our content with just minor variations between versions. We also work with many different product managers and need an efficient and reliable way to send and track review and approval assignments. The company is growing fast, and we are leveraging Paligo's powerful features to increase our efficiency.
  • Content Management.
  • Publishing to Multiple Outputs.
  • Allowing Collaboration and Review with SMEs.
  • Excellent Product Documentation, LMS Resources, and Support.
  • Layout editor could be more efficient and flexible.
Paligo is an extremely powerful tool that can be scaled to fit an organization. It can be considered a tool just for technical documentation, but it also could manage documentation for an entire organization. We are a medium-sized technical writing team with a fairly large portfolio of products to manage, and it makes sense for us to use it just as a writing team. But we are also working on connecting with other teams to get them on board so we can all share content across the enterprise. That's where the investment in Paligo really will pay off richly. The only situation I can think of where it would not work is for a very small company with just one product that doesn't plan on growing much.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Paligo to write, edit, update, and manage our product support website.

With our last documentation tool, it was necessary to download a desktop application, connect it to the repo containing the support site, and then download the entire site if we needed to edit something; publishing the site meant pushing it back to the repo and then deploying it. Paligo simplified this process by handling everything within a web browser. Critically, this allows us to update and deploy documentation from any machine with an internet connection, without having to download and authenticate an entire application.

Paligo also makes it easier for us to centralize our product documentation, as well as streamlining the process of creating, editing, and publishing new pages as we add new features to the product.
  • Creating and editing documentation is easy
  • Custom CSS and JS makes it simple to customize the site to our exact needs
  • Integrations with multiple services (Azure, Bitbucket, etc.) give us multiple options for deploying docs
  • Collaborative editing is straightforward
  • The amount of CSS/JS required to customize a site's appearance can be cumbersome
  • Product documentation can be lacking, specifically with integrations; in some cases, support offered no real help when trying to solve a problem with an integrated service
  • Some features require extensive development experience to use, which can sometimes be an obstacle to less-experienced team members
Paligo is an excellent solution for companies looking to move to a cloud-based writing and deployment tool for product documentation. It can be especially useful for companies that need to have multiple support sites connected to a single hub page.

There can be a steep learning curve when using Paligo, as not everything is as obvious as one might hope. Nevertheless, once you know the product, it's very useful.
Rachel Cheyfitz she/her | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
1. PDF & Word generation to enable partner rebranding.
2. Push to Bitbucket for HTML5 embedded.
3. Push to Zendesk.
  • Zendesk integration is fantastic.
  • Single sourcing is amazing.
  • File management is easy and intuitive.
  • More flexible PDF formatting.
  • Self hosting platform.
  • Bi-directional open source repo syncs for true CI/CD.
  • API integration.
For any cloud-based documentation needs for any size company, if single sourcing is a priority, Paligo exceeds its major competitor. Because it was born in the cloud, its cloud-based features make it far more intuitive.
Monica White | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
We use Paligo in the Technical Documentation department to structure and publish the software guides. We use the Salesforce integration to push the content to Support and the HTML5 publication capacity to publish directly to internal access.
The ability to cross-reference and reuse content allows our technical writers to be succinct in topics while still presenting useful information across multiple products with a consistent message throughout.
  • The topic/publication structure is quite graceful. It makes setting up an outline of content quite intuitive, and after the tools are identified and defined, it's much simpler to set up a large document and work with others to produce it.
  • Strict field definitions and use cases make topic structuring inherent in the workflow, which brings more attention to content handling. The train of thought required to utilize the tool also improves the train of thought required to focus the content, making for a better ultimate publication.
  • The output capabilities and Salesforce integration make publishing the files very easy.
  • The learning curve is a bit steep, especially for anyone who's never worked in a true content authoring tool before. It takes a bit of work to move from a Word atmosphere to Paligo, but the training sessions address all of those issues and more.
  • I wish there were more focused formatting tools. At this point, I don't know how to change the text color or format my output beyond the legacy defaults I inherited when I started this job. My fellow writers and I still sometimes struggle with putting things where we want them to go simply because they aren't the right field type at that location.
Before I took the intermediate training, I was so frustrated with Paligo that I mentioned it negatively in a networking event. Now that I have taken the training, I will be correcting that comment at the next one. :)
However, part of what I inherited was a badly managed library, and I am working hard with my fellow writers to restructure and re-present the content. I have only been working with Paligo for a month and a half, and while it's been a struggle to get here, I'm glad I learned it so that I can truly utilize its content reuse strengths across three different product lines.
It probably would not be ideal for desktop layout or on-demand production environments.
Sarah Holdgrafer | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Currently, only my team uses Paligo. My team creates end-user help articles through ZenDesk Guide. Paligo is a CCMS that allows us to use structured authoring to manage all our content and publish not just to ZenDesk, but to PDF and HTML5 as well.

Paligo allows us to single source the majority of our end-user content, reuse topics across multiple articles, publish to multiple channels, filter for languages and markets by country, manage content in an intuitive way, and remove all styling concerns from the content creation process so we can focus just on writing the content and managing article images and gifs. Our article styles are handled all through our external CSS, which automatically applies to articles when we publish to Zendesk. This makes our content creation process shorter overall and allows us to reuse content in multiple formats with different styling, without creating the content from scratch each time.

In addition to managing our knowledge base content, we've also created feature-level user guides in PDF to distribute to select users, and PDF guides to send to developer partners as product documentation required for the plugin development approval process.
  • Topic reuse - many of our tutorial and how-to articles include procedures with the same first steps. Reuse allows us to create these steps once, including images, and reuse them in as many articles as we need.
  • Single sourcing - At any time if the text or images in reused topics need updating, we just update the original topic and the changes reflect in every article that uses that topic.
  • Content management - the topic and media management is excellent. we can organize however we need, rename topics and images as needed and move them around within the folder structure without breaking any links to the topics / articles they are used in (each topic and asset has a unique ID number that doesn't change, allow us to rename and move assets to best suit our needs)
  • Filtering and variables - we can create a single topic that includes all the information for different markets (in this case, different content for accounts in different countries) and by using filtering and variables when building the content and in the publishing workflow I can publish just the US content to our US help center, the UK content to the UK help center, and the Australian content to the Australia help center, but using manage a single article within Paligo itself.
  • Translation and localization workflow - the translation workflow (sending topics to be translated into another language) and localization workflow (publishing the same content in multiple languages) works well within the ZenDesk integration. It uses the ZenDesk localization settings to ensure the proper translation ends up in the correct articlein Zendesk.
  • Speed - since it is cloud-based we do sometimes run into speed issues in loading or saving content
  • steep learning curve requiring training - the Paligo trainer is great, and their help center is also very good, but for individuals not already well versed in structured authoring it's a bit of an uphill battle to really understand why the UI works the way it does. that said, their support is incredibly helpful and enthusiastic!
  • Stats - it would be great to have easier access to data showing which users on my team have created what content and performed what actions within the app or on specific content. This is mostly a manager need as I need to report progress to my manager regularly.
A recommendation would be dependent on their needs and numerous other factors, including their publishing channels. For my situation, where a good chunk of content (especially images) are used across dozens of articles, we're documenting the use of an entire SaaS platform and the 100+ integrations we have, and we publish different versions of some content based on account country, it's an ideal fit. Any help center that has more than 100 articles hosted on ZenDesk could potentially benefit from switching to a cloud-based CCMS.

Structured authoring is less appropriate for managing content that is constantly changing or doesn't have a unified structure, like blogs, for instance.
Return to navigation